MarkLogic 12 Product Documentation
PUT /manage/v2/privileges/{id|name}/properties

Summary

This resource address can be used to update the properties for the specified privilege. The only thing you can change about a privilege is the set of associated roles.

URL Parameters
format	The format of the posted data. Can be either `json` (default) or `xml`. This value overrides the Accept header if both are present.
kind	The kind of privilege. Can be either `execute` or `uri`.

Request Headers
Accept	The expected MIME type of the response. If the `format` parameter is present, it takes precedence over the Accept header.
Content-type	The MIME type of the data in the request body, either `application/xml` or `application/json`.

Response Headers
Content-type	The MIME type of the data in the response body. Depending upon the value of the `format` parameter or Accept header, either `application/xml` or `application/json`.

Response

Upon success, MarkLogic Server returns status code 204 (No Content). If the payload is malformed or the privilege does not exist, a status code of 400 (Bad Request) is returned. A status code of 401 (Unauthorized) is returned if the user does not have the necessary privileges.

Required Privileges

This operation requires one of the following:

the manage-admin and security role
the following privileges:
http://marklogic.com/xdmp/privileges/manage

http://marklogic.com/xdmp/privileges/manage-admin

http://marklogic.com/xdmp/privileges/privilege-set-roles

Usage Notes

The properties that can be modified are listed here.

Note: The properties described here are for XML payloads. In general they are the same for JSON, with the exception that, in JSON, roles is expressed in singular form. For example, in JSON, roles is instead role and the format is: "role":["rolename"].

The structure of the output returned from this REST API is as follows:

privilege-name

Privilege name (unique)

action

A URI to protect.

kind

A protected "action" (or object).

roles

The roles assigned. The roles assigned to the user.

This is a complex structure with the following children:

role: A role identifier (unique key).

Example